<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
        <link rel="stylesheet" type="text/css" href="../../styles.css" />
        <title>
            CSC207H: Project, Phase III
        </title>
    </head>
    <body>
        <h1>
            CSC207H: Project, Phase III
        </h1>
        <h2>
            Due Date
        </h2>
        <p>
            The final phase of the project is due Friday 4 December at 11:59pm.
        </p>
        <p>
            The deadline for putting together your next sprint backlog is Monday 30 November at 5pm. If you get a first draft done earlier, please let your ScrumMaster know.
        </p>
        <h2>
            Overview (both service-learning and regular teams)
        </h2>
        <p>
            Continue where you left off from Phase II. Follow the Scrum process for the next sprint.
        </p>
        <h2>
            Team member evaluations (both service-learning and regular teams)
        </h2>
        <p>
            We will post peer evaluations for Phase III late next week.
        </p>
        <p>
            Your Phase II will receive a grade, and these evaluations will be used to make individual adjustments to that grade. In the case of serious disagreement, or if you request it, we will hold a team meeting to discuss the results, but we will never reveal individual ratings.
        </p>
        <h2>
            Sprint backlog (both service-learning and regular teams)
        </h2>
        <p>
            To start Phase III, your team needs to work out its sprint backlog.
        </p>
        <p>
            For many teams, the Phase II sprint backlog was not particularly done well. Please reread the <a href="http://www.cdf.utoronto.ca/~csc207h/fall/lectures/L5101/w5/Scrum.pdf">Scrum slides</a> and also the various <a href="http://www.agilecollab.com/sprint-planning-meeting">articles about sprints on agilecollab.net</a> for the proper way to use a sprint backlog.
        </p>
        <p>
            Your sprint backlog will be marked not only on content but also on clarity, structure (please don't make a mess), grammar, and spelling. You will be marked strictly on this for Phase III, so plan to do a little background reading.
        </p>
        <h2>
            Testing
        </h2>
        <p>
            As described in the Scrum lecture notes and in every description of Scrum on the web, you need to keep your testing up to date with your code. You will be marked strictly on this for Phase III.
        </p>
        <p>
            Unit tests are great for non-GUI code. To test GUI code, please write a series of short scripts that a tester can follow. Put these on a page in your wiki.
        </p>
        <p>
            As an example, you might have something like this as one of your GUI tests:
        </p>
        <ul>
            <li>Run the application.
            </li>
            <li>Select "View Next Task"
            </li>
            <li>Select "Enter Solution/Password"
            </li>
            <li>Enter "cow"
            </li>
            <li>You should see a confirmation and then be taken to the second task.
            </li>
        </ul>
        <h2>
            User Guide (both service-learning and regular teams)
        </h2>
        <p>
            You should continue your user guide as described in the Phase II handout. For regular teams, you should describe the file format you choose in addition to the parts for the users of your program. Be sure to make clear which sections are for users and which are for administrators.
        </p>
        <h2>
            "Daily" status report (both service-learning and regular teams)
        </h2>
        <p>
            Please email three status reports to your team's DrProject mailing list during the week of 30 November. They should happen before noon on Monday, before noon on Wednesday, and before noon on Friday. Address these questions:
        </p>
        <ul>
            <li>What did you accomplish since the last report?
            </li>
            <li>What do you plan to do in the next couple of days?
            </li>
            <li>What obstacles are in your way?
            </li>
        </ul>
        <p>
            Emails must be clear, effectively structured, and contain proper spelling and grammar. Bullet points are fine.
        </p>
        <h2>
            The end of the sprint (both service-learning and regular teams)
        </h2>
        <p>
            At the end of the sprint, your team should have a working version of a mobile application that does the entire product backlog.  Please include a README file in your repository telling your ScrumMaster where to find your Phase III project and user guide.  Feel free to tell them anything else that you think will help them navigate your work.
        </p>
    </body>
</html>
